PDOs for AKD, AKD2G, AKD-N, S300, or S700

The KAS Motion Engine interacts with the AKD, AKD2G, AKD-N, S300Closed "Servostar 300 drive" See Servo Drive in Glossary, or S700Closed "Servostar 700 drive" See Servo Drive in Glossary drives through CANopen objects in the selected PDOs.

  • Some of the ML and MC function blocks require specific CANopen objects in the PDOs.
  • Defaults:
    • AKD, AKD2G, and AKD-N PDOs include all of the CANopen objects needed by the motion engine and function blocks.
    • S300 and S700 PDOs include only the minimal CANopen objects required by the KAS motion engine.

PDO Types

Examples

These are examples where the PDOClosed PDO is a type of protocol frame used in some fieldbuses. A PDO contains one or more object dictionary entries, which define the application data transferred between devices. object is passed as an argument in the function block.

Example 1

MLSmpConECAT( PipeNetwork.SMP1, 1001, 16#2050, 0);

Where:

Example 2

MLCNVConnectEx(PipeNetwork.CNV1, PipeNetwork.AXIS1, EC_ADDITIVE_TORQUE_VALUE, 0 ) ;

The argument is a constant based on the object index.

Example 3

MLSmpConPNAxis(PipeNetwork.SMP1, PipeNetwork.AXIS1, ML_SECOND_FEEDBACK_POSITION);

Where:

ML_SECOND_FEEDBACK_POSITION specifies the secondary actual position from the Pipe Network Axis.


  • The ML_SECOND_FEEDBACL_POSITION constant has been deprecated and only AKD devices supported it.
    It is deprecated because the AKD2G supports more than one secondary feedback.

Concept Link IconSee Also